Claiming ownership of tracking devices

ABSTRACT

A mobile phone connected to a tracking system detects the presence of a nearby tracking device. If the tracking device is detected for more than a threshold amount of time, the tracking system can instruct the mobile phone to generate a user notification prompting a user to claim ownership of the tracking device. After the user claims ownership of the tracking device, the mobile device provides the ownership claim to the tracking system which can associate the tracking device with that user&#39;s account in the tracking system, enabling the user to access features of the tracking device and tracking system reserved for owners of that tracking device.

CROSS REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. application Ser. No.16/74,219, filed Feb. 12, 2019, now U.S. Pat. No. 11,172,037, which isincorporated by reference in its entirety.

BACKGROUND

This disclosure relates generally to tracking devices, and morespecifically, to claiming ownership of tracking devices.

Electronic tracking devices track the location of people and/or objects.For example, a user can use GPS technology to track a device remotelyand determine a location of a user of the device. In another example, auser can attach a tracking device to an important object, such as keysor a wallet, and use the features of the tracking device to more quicklylocate the object, (e.g., if it becomes lost).

A tracking device can have multiple owners in its lifetime. Forinstance, a first owner of a tracking device may physically transfer thetracking device to a second owner. Accordingly, there is a need for toenable the second owner to claim ownership of the tracking device with acentral tracking system associated with the tracking device.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates an example tracking system environment in which atracking device can operate, according to one embodiment.

FIG. 2 illustrates an example tracking system for use in a trackingsystem environment, according to one embodiment.

FIG. 3 illustrates an example user mobile device for use in a trackingsystem environment, according to one embodiment.

FIG. 4 illustrates an example community mobile device for use in atracking system environment, according to one embodiment.

FIG. 5 illustrates an example tracking device for use in a trackingsystem environment, according to one embodiment.

FIG. 6 illustrates an example environment in which a user may claimownership of a tracking device, according to one embodiment.

FIG. 7 is a flow chart of a method for claiming ownership of a trackingdevice, according to one embodiment.

The figures depict various embodiments of the present invention forpurposes of illustration only. One skilled in the art will readilyrecognize from the following discussion that alternative embodiments ofthe structures and methods illustrated herein may be employed withoutdeparting from the principles of the invention described herein.

DETAILED DESCRIPTION

Environment Overview

Embodiments described herein detail functionality associated with atracking device. A user can attach a tracking device to or enclose thetracking device within an object, such as a wallet, keys, a car, a bike,a pet, or any other object that the user wants to track. Or, a trackingdevice can be a device with a primary purpose unrelated to trackingfunctionality (e.g., a set of headphones, an electronic key, a wirelessspeaker, a fitness tracker, a camera) that has an integrated trackingcomponent that allows the device to be tracked. The user can then use amobile device (e.g., by way of a software application installed on themobile device) or other device or service to track the tracking device.For example, the mobile device can perform a local search for a trackingdevice. However, in situations where the user is unable to locate thetracking device using their own mobile device (e.g., if the trackingdevice is beyond a distance within which the mobile device and thetracking device can communicate), the user can leverage the capabilitiesof a community of users of a tracking device system as described below.

A tracking system (also referred to herein as a “cloud server,”“tracking server,” or simply “server”) can maintain user profilesassociated with a plurality of users of the tracking system. Thetracking system can associate each user within the system with one ormore tracking devices associated the user (e.g., tracking devices thatthe user has purchased and is using to track objects owned by the user,or devices that include a tracking component and have additionalnon-tracking features). If the user's tracking device, or the object towhich the tracking device is attached, becomes lost or stolen, the usercan send an indication that the tracking device is lost to the trackingsystem, which is in communication with one or more mobile devicesassociated with the community of users in communication with the system.The tracking system can set a flag indicating the tracking device islost. When one of a community of mobile devices that are scanning fornearby tracking devices and providing updated locations to the trackingsystem identifies a flagged tracking device, the tracking system canassociate the received location with the flagged tracking device, andrelay the location to a user of the tracking device, thereby enablingthe user to locate the lost tracking device. As used herein, “mobiledevice” can refer to a phone, tablet computer, or other connecteddevice, and can also refer to systems typically not consider mobile,such as servers, routers, gateways, access points, and specializedsystems configured to couple to tracking devices and report a locationof the tracking devices.

As used herein, “tracking device” can refer to any device configured tocommunicate with another device for the purpose of locating the trackingdevice. Tracking devices can be specialized or single-purpose devices(e.g., self-contained devices that include circuitry or components tocommunicate with another device). However, “tracking device” as usedherein can also refer to device or object with a different primaryfunction but with secondary tracking device functionality. For example,a wireless speaker can include tracking device components that allow auser to track and/or locate the wireless speaker. In some embodiments, atracking device platform can be established such that devices andobjects that satisfy one or more criteria can act as tracking deviceswithin a tracking device ecosystem. For instance, a tracking deviceprovider can provide an SDK or custom chipset that, when incorporatedinto an object or device, enable the object or device to function astracking devices, to communicate with other devices within the trackingdevice ecosystem, and to implement the functionalities described herein.

FIG. 1 illustrates an example tracking system environment in which atracking device can operate, according to one embodiment. Theenvironment of FIG. 1 includes a tracking system 100 communicativelycoupled to a mobile device 102 associated with the user 103 via a firstnetwork 108. The tracking system 100 is also communicatively coupled toa plurality of community mobile devices 104 a through 104 n(collectively referred to herein as “community mobile devices 104”)associated with a plurality of users 105 a through 105 n of the trackingsystem 100 (collectively referred to herein as “community users 105”)via the first network 108. As will be explained in more detail below,the tracking system 100 can allow the user 103 to manage and/or locate atracking device 106 associated with the user 103. In some embodiments,the tracking system 100 leverages the capabilities of community mobiledevices 104 to locate the tracking device 106 if the location of thetracking device is unknown to the user 103 and beyond the capabilitiesof mobile device 102 to track. In some configurations, the user 103 mayown and register multiple tracking devices 106. Although FIG. 1illustrates a particular arrangement of the tracking system 100, mobiledevice 102, community mobile devices 104, and tracking device 106,various additional arrangements are possible.

In some configurations, the user 103 may be part of the community ofusers 105. Further, one or more users 105 may own and register one ormore tracking devices 106. Thus, any one of the users within thecommunity of users 105 can communicate with tracking system 100 andleverage the capabilities of the community of users 105 in addition tothe user 103 to locate a tracking device 106 that has been lost.

The tracking system 100, mobile device 102, and plurality of communitymobile devices 104 may communicate using any communication platforms andtechnologies suitable for transporting data and/or communicationsignals, including known communication technologies, devices, media, andprotocols supportive of remote data communications.

In certain embodiments, the tracking system 100, mobile device 102, andcommunity mobile devices 104 may communicate via a first network 108,which may include one or more networks, including, but not limited to,wireless networks (e.g., wireless communication networks), mobiletelephone networks (e.g., cellular telephone networks), closedcommunication networks, open communication networks, satellite networks,navigation networks, broadband networks, narrowband networks, theInternet, local area networks, and any other networks capable ofcarrying data and/or communications signals between the tracking system100, mobile device 102, and community mobile devices 104. The mobiledevice 102 and community of mobile devices 104 may also be incommunication with a tracking device 106 via a second network 110. Thesecond network 110 may be a similar or different type of network as thefirst network 108. In some embodiments, the second network 110 comprisesa wireless network with a limited communication range, such as aBluetooth or Bluetooth Low Energy (BLE) wireless network. In someconfigurations, the second network 110 is a point-to-point networkincluding the tracking device 106 and one or more mobile devices thatfall within a proximity of the tracking device 106. In such embodiments,the mobile device 102 and community mobile devices 104 may only be ableto communicate with the tracking device 106 if they are within a closeproximity to the tracking device, though in other embodiments, thetracking device can use long-distance communication functionality (forinstance, a GSM transceiver) to communicate with either a mobile device102/104 or the tracking system 100 at any distance. In someconfigurations, the mobile device 102 and one or more community mobiledevices 104 may each be associated with multiple tracking devicesassociated with various users.

As mentioned above, FIG. 1 illustrates the mobile device 102 associatedwith the user 103. The mobile device 102 can be configured to performone or more functions described herein with respect to locating trackingdevices (e.g., tracking device 106). For example, the mobile device 102can receive input from the user 103 representative of information aboutthe user 103 and information about a tracking device 106. The mobiledevice 102 may then provide the received user information, trackingdevice information, and/or information about the mobile device 102 tothe tracking system 100. Accordingly, the tracking system 100 is able toassociate the mobile device 102, the user 103, and/or the trackingdevice 106 with one another. In some embodiments, the mobile device 102can communicate with the tracking device 106 and provide informationregarding the location of the tracking device to the user 103. Forexample, the mobile device 102 can detect a communication signal fromthe tracking device 106 (e.g., by way of second network 110) as well asa strength of the communication signal or other measure of proximity todetermine an approximate distance between the mobile device 102 and thetracking device 106. The mobile device 102 can then provide thisinformation to the user 103 (e.g., by way of one or more graphical userinterfaces) to assist the user 103 to locate the tracking device 106.Accordingly, the user 103 can use the mobile device 102 to track andlocate the tracking device 106 and a corresponding object associatedwith the tracking device 106. If the mobile device 102 is located beyondthe immediate range of communication with the tracking device 106 (e.g.,beyond the second network 110), the mobile device 102 can be configuredto send an indication that a tracking device 106 is lost to the trackingsystem 100, requesting assistance in finding the tracking device. Themobile device 102 can send an indication of a lost device in response toa command from the user 103. For example, once the user 103 hasdetermined that the tracking device 106 is lost, the user can provideuser input to the mobile device 102 (e.g., by way of a graphical userinterface), requesting that the mobile device 102 send an indicationthat the tracking device 106 is lost to the tracking system 100. In someexamples, the lost indication can include information identifying theuser 103 (e.g., name, username, authentication information), informationassociated with the mobile device 102 (e.g., a mobile phone number),information associated with the tracking device (e.g., a unique trackingdevice identifier), or a location of the user (e.g., a GPS location ofthe mobile device 102 at the time the request is sent).

The tracking system 100 can be configured to provide a number offeatures and services associated with the tracking and management of aplurality of tracking devices and/or users associated with the trackingdevices. For example, the tracking system 100 can manage informationand/or user profiles associated with user 103 and community users 105.In particular, the tracking system 100 can manage information associatedwith the tracking device 106 and/or other tracking devices associatedwith the user 103 and/or the community users 105.

As mentioned above, the tracking system 100 can receive an indicationthat the tracking device 106 is lost from the mobile device 102. Thetracking system 100 can then process the indication in order to help theuser 103 find the tracking device 106. For example, the tracking system100 can leverage the capabilities of the community mobile devices 104 tohelp find the tracking device 106. In particular, the tracking system100 may set a flag for a tracking device 106 to indicate that thetracking device 106 lost and monitor communications received from thecommunity mobile devices 104 indicating the location of one or moretracking devices 106 within proximity of the community mobile devices104. The tracking system 100 can determine whether a specific locationis associated with the lost tracking device 106 and provide any locationupdates associated with the tracking device 106 to the mobile device102. In one example, the tracking system may receive constant updates oftracking device 106 locations regardless of whether a tracking device106 is lost and provide a most recent updated location of the trackingdevice 106 in response to receiving an indication that the trackingdevice 106 is lost.

In some configurations, the tracking system 100 can send a locationrequest associated with the tracking device 106 to each of the communitymobile devices 104. The location request can include any instructionsand/or information necessary for the community mobile devices 106 tofind the tracking device 102. For example, the location request caninclude a unique identifier associated with the tracking device 106 thatcan be used by the community mobile devices 104 to identify the trackingdevice 106. Accordingly, if one of the community mobile devices 104detects a communication from the tracking device 106 (e.g., if thecommunity mobile device 104 is within range or moves within range of thecommunication capabilities of the tracking device 106 and receives asignal from the tracking device 106 including or associated with theunique identifier associated with the tracking device 106), thecommunity mobile device 104 can inform the tracking system 100. Usingthe information received from the community mobile devices 104, thetracking system 100 can inform the user (e.g., by way of the mobiledevice 102) of a potential location of the tracking device 106.

As shown in FIG. 1 and as mentioned above, the tracking system 100 cancommunicate with a plurality of community mobile devices 104 associatedwith corresponding community users 105. For example, an implementationmay include a first community mobile device 104 a associated with afirst community user 105 a, a second community mobile device 104 bassociated with a second community user 105 b, and additionalcommunication mobile devices associated with additional community usersup to an nth community mobile device 104 n associated with an nthcommunity user 105 n. The community mobile devices 104 may also includefunctionality that enables each community mobile device 104 to identifya tracking device 106 within a proximity of the community mobile device104. In one example, a first community mobile device 104 a withinproximity of a tracking device 106 can communicate with the trackingdevice 106, identify the tracking device 106 (e.g., using a uniqueidentifier associated with the tracking device 106), and/or detect alocation associated with the tracking device 106 (e.g., a location ofthe first mobile community device 104 a at the time of the communicationwith the tracking device 106). This information can be used to provideupdated locations and/or respond to a location request from the trackingsystem 100 regarding the tracking device 106. In some embodiments, thesteps performed by the first community mobile device 104 a can be hiddenfrom the first community user 105 a. Accordingly, the first communitymobile device 104 a can assist in locating the tracking device 106without bother and without the knowledge of the first community user 105a.

As mentioned above, the tracking system 100 can assist a user 103 inlocating a tracking device 106. The tracking device may be a chip, tile,tag, or other device for housing circuitry and that may be attached toor enclosed within an object such as a wallet, keys, purse, car, orother object that the user 103 may track. Additionally, the trackingdevice 106 may include a speaker for emitting a sound and/or atransmitter for broadcasting a beacon. In one configuration, thetracking device 106 may periodically transmit a beacon signal that maybe detected using a nearby mobile device 102 and/or community mobiledevice 104. In some configurations, the tracking device 106 broadcasts abeacon at regular intervals (e.g., one second intervals) that may bedetected from a nearby mobile device (e.g., community mobile device104). The strength of the signal emitted from the tracking device 106may be used to determine a degree of proximity to the mobile device 102or community mobile device 104 that detects the signal. For example, ahigher strength signal would indicate a close proximity between thetracking device 106 and the mobile device 102 and a lower strengthsignal would indicate a more remote proximity between the trackingdevice 106 and the mobile device 102, though in some embodiments, thetracking device 106 can intentionally vary the transmission strength ofthe beacon signal. In some cases, the strength of signal or absence of asignal may be used to indicate that a tracking device 106 is lost.

System Overview

FIG. 2 illustrates an example tracking system for use in a trackingsystem environment, according to one embodiment. As shown, the trackingsystem 100 may include, but is not limited to, an association manager204, a tracking device location manager 206, and a data manager 208,each of which may be in communication with one another using anysuitable communication technologies. It will be recognized that althoughmanagers 204-208 are shown to be separate in FIG. 2 , any of themanagers 204-208 may be combined into fewer managers, such as into asingle manager, or divided into more managers as may serve a particularembodiment.

The association manager 204 may be configured to receive, transmit,obtain, and/or update information about a user 103 and/or informationabout one or more specific tracking devices (e.g., tracking device 106).In some configurations, the association manager 204 may associateinformation associated with a user 103 with information associated witha tracking device 106. For example, user information and trackinginformation may be obtained by way of a mobile device 102, and theassociation manager 204 may be used to link the user information andtracking information. The association between user 103 and trackingdevice 106 may be used for authentication purposes, or for storing userinformation, tracking device information, permissions, or otherinformation about a user 103 and/or tracking device 106 in a database.

The tracking system 100 also includes a tracking device location manager206. The tracking device location manager 206 may receive and process anindication that the tracking device 106 is lost from a mobile device(e.g., mobile device 102 or community mobile devices 104). For example,the tracking system 100 may receive a lost indication from a mobiledevice 102 indicating that the tracking device 106 is lost. The trackingdevice location manager 206 may set a flag on a database (e.g., trackerdatabase 212) indicating that the tracking device 106 is lost. Thetracking device location manager 206 may also query a database todetermine tracking information corresponding to the associated user 103and/or tracking device 106. The tracking system 100 may obtain trackingdevice information and provide the tracking device information or otherinformation associated with the tracking device 106 to a plurality ofcommunity mobile devices 104 to be on alert for the lost or unavailabletracking device 106.

The tracking device location manager 206 may also receive a locationfrom one or more community mobile devices 104 that detect the trackingdevice 106, for instance in response to the community mobile devicereceiving a beacon signal transmitted by the tracking device 106,without the tracking device 106 having been previously marked as lost.In such embodiments, a user corresponding to the mobile device 102 canrequest a most recent location associated with the tracking device fromthe tracking system 100, and the location manager 206 can provide thelocation received from the community mobile device for display by themobile device 102. In some embodiments, the location manager 206provides the location of the tracking device 106 received from acommunity mobile device either automatically (for instance if thetracking device 106 is marked as lost) or at the request of a user ofthe mobile device 102 (for instance, via an application on the mobiledevice 102). The location manager 206 can provide a location of atracking device 106 to a mobile device 102 via a text message, pushnotification, application notification, automated voice message, or anyother suitable form of communication.

The tracking device location manager 206 may further manage providingindications about whether a tracking device 106 is lost or not lost. Forexample, as discussed above, the tracking device location manager 206may provide a location request to the community of mobile devices 104indicating that a tracking device 106 is lost. Additionally, uponlocation of the tracking device 106 by the user 103 or by one of thecommunity of users 105, the tracking device location manager 206 mayprovide an indication to the user 103, community user 105, or trackingsystem 100 that the tracking device 106 has been found, thus removingany flags associated with a tracking device and/or canceling anylocation request previously provided to the community of users 105. Forexample, where a user 103 sends an indication that the tracking device106 is lost to the tracking system 100 and later finds the trackingdevice 106, the mobile device 102 may provide an indication to thetracking system 100 that the tracking device 106 has been found. Inresponse, the tracking device location manager 206 may remove a flagindicating that the tracking device 106 is lost and/or provide anupdated indication to the community of users 105 that the trackingdevice 106 has been found, thus canceling any instructions associatedwith the previously provided location request. In some configurations,the notification that the tracking device 106 has been found may beprovided automatically upon the mobile device 102 detecting the trackingdevice 106 within a proximity of the mobile device 102. Alternatively,the notification that the tracking device 106 has been found may beprovided by the user 103 via user input on the mobile device 102. Inanother example, a known user (e.g., a friend or family member) withwhom the tracking device 106 has been shared may provide an indicationthat the tracking device 106 has been found.

The tracking system 100 additionally includes a data manager 208. Thedata manager 208 may store and manage information associated with users,mobile devices, tracking devices, permissions, location requests, andother data that may be stored and/or maintained in a database related toperforming location services of tracking devices. As shown, the datamanager 208 may include, but is not limited to, a user database 210, atracker database 212, permissions data 214, and location request data216. It will be recognized that although databases and data within thedata manager 208 are shown to be separate in FIG. 2 , any of the userdatabase 210, tracker database 212, permissions data 214, and locationrequest data 216 may be combined in a single database or manager, ordivided into more databases or managers as may serve a particularembodiment.

The data manager 208 may include the user database 210. The userdatabase 210 may be used to store data related to various users. Forexample, the user database 210 may include data about the user 103 aswell as data about each user 105 in a community of users 105. Thecommunity of users 105 may include any user that has provided userinformation to the tracking system 100 via a mobile device 102, 104 orother electronic device. The user information may be associated with oneor more respective tracking devices 106, or may be stored without anassociation to a particular tracking device. For example, a communityuser 105 may provide user information and permit performance of trackingfunctions on the community mobile device 104 without owning or beingassociated with a tracking device 106. The user database 210 may alsoinclude information about one or more mobile devices or other electronicdevices associated with a particular user.

The data manager 208 may also include a tracker database 212. Thetracker database 212 may be used to store data related to trackingdevices. For example, the tracker database 212 may include tracking datafor any tracking device 106 that has been registered with the trackingsystem 100. Tracking data may include unique tracker identifications(IDs) associated with individual tracking devices 106. Tracker IDs maybe associated with a respective user 103. Tracker IDs may also beassociated with multiple users. Additionally, the tracker database 212may include any flags or other indications associated with whether aspecific tracking device 106 has been indicated as lost and whether anyincoming communications with regard to that tracking device 106 shouldbe processed based on the presence of a flag associated with thetracking device 106.

The data manager 208 may further include permissions data 214 andlocation request data 216. Permissions data 214 may include levels ofpermissions associated with a particular user 103 and/or tracking device106. For example, permissions data 214 may include additional users thathave been indicated as sharing a tracking device 106, or who have beengiven permission to locate or receive a location of a tracking device106. Location request data 216 may include information related to alocation request or a lost indication received from the user 103 via amobile device 102.

FIG. 3 illustrates an example user mobile device for use in a trackingsystem environment, according to one embodiment. As shown, the mobiledevice 102 may include, but is not limited to, a user interface manager302, a location request manager 304, a database manager 306, and atracking manager 308, each of which may be in communication with oneanother using any suitable communication technologies. It will berecognized that although managers 302-308 are shown to be separate inFIG. 3 , any of the managers 302-308 may be combined into fewermanagers, such as into a single manager, or divided into more managersas may serve a particular embodiment.

As will be explained in more detail below, the mobile device 102includes the user interface manager 302. The user interface manager 302may facilitate providing the user 103 access to data on a trackingsystem 100 and/or providing data to the tracking system 100. Further,the user interface manager 302 provides a user interface by which theuser 103 may communicate with tracking system 100 and/or tracking device106 via mobile device 102.

The mobile device 102 may also include a location request manager 304.The location request manager 304 may receive and process a request inputto the mobile device 102 to send an indication that a tracking device106 is lost to a tracking system 100. For example, the user 103 mayprovide an indication that a tracking device 106 is lost, unreachable,or otherwise unavailable, from the mobile device 102 via the userinterface manager 302, and the location request manager 304 may processthe lost indication and provide any necessary data to the trackingsystem 100 for processing and relaying a location request to other users105 over a network 108. In some configurations, an indication that atracking device 106 is lost is provided via user input. Alternatively,the indication may be transmitted automatically in response to themobile device 102 determining that a tracking device 106 is lost.

In addition, the location request manager 304 can request a location ofthe tracking device 106 without the tracking device 106 being identifiedas lost. For instance, a user can access a tracking device locationfeature of an application running on the mobile device 102 (for example,via the user interface manager 302), and the location request manager304 can request a most recent location of the tracking device 106 fromthe tracking system 100. The location request manager 304 can receivethe most recent location from the tracking system 100, and can displaythe most recent location via the user interface manager 302.

The mobile device 102 may also include a database manager 306. Thedatabase manager 306 may maintain data related to the user 103, trackingdevice 106, permissions, or other data that may be used for locating atracking device 106 and/or providing a request to a tracking system 100for locating one or more tracking devices 106 associated with the user103. Further, the database manager 306 may maintain any information thatmay be accessed using any other manager on the mobile device 102.

The mobile device 102 may further include a tracking manager 308. Thetracking manager 308 may include a tracking application (e.g., asoftware application) for communicating with and locating a trackingdevice 106 associated with the user 103. For example, the trackingmanager 308 may be one configuration of a tracking application installedon the mobile device 102 that provides the functionality for locating atracking device 106 and/or requesting location of a tracking device 106using a tracking system 100 and/or a plurality of community mobiledevices 104. As shown, the tracking manager 308 may include, but is notlimited to, a Bluetooth Low Energy (BLE) manager 310, a persistencemanager 312, a local files manager 314, a motion manager 316, a securestorage manager 318, a settings manager 320, a location manager 322, anetwork manager 324, a notification manager 326, a sound manager 328, afriends manager 330, a photo manager 332, an authentication manager 334,and a device manager 336. Thus, the tracking manager 308 may perform anyof the functions associated with managers 310-338, described inadditional detail below.

The BLE manager 310 may be used to manage communication with one or moretracking devices 106. The persistence manager 312 may be used to storelogical schema information that is relevant to the tracking manager 308.The local files manager 314 may be responsible for managing all filesthat are input or output from the mobile device 102. The motion manager316 may be responsible for all motion management required by thetracking manager 308. The secure storage manager may be responsible forstorage of secure data, including information such as passwords andprivate data that would be accessed through this sub-system. Thesettings manager 320 may be responsible for managing settings used bythe tracking manager 308. Such settings may be user controlled (e.g.,user settings) or defined by the tracking manager 308 for internal use(e.g., application settings) by a mobile device 102 and/or the trackingsystem 100. The location manager 322 may be responsible for all locationtracking done by the tracking manager 308. For example, the locationmanager 322 may manage access to the location services of the mobiledevice 102 and works in conjunction with other managers to persist data.The network manager 324 may be responsible for all Internetcommunications from the tracking manager 308. For example, the networkmanager 324 may mediate all Internet API calls for the tracking manager308. The notification manager 326 may be responsible for managing localand push notifications required by the tracking manager 308. The soundmanager 328 may be responsible for playback of audio cues by thetracking manager 308. The friends manager 330 may be responsible formanaging access to contacts and the user's social graph. The photomanager 332 may be responsible for capturing and managing photos used bythe tracking manager 308. The authentication manager 334 may beresponsible for handling the authentication (e.g., sign in or login) ofusers. The authentication manager 334 may also include registration(e.g., sign up) functionality. The authentication manager 334 furthercoordinates with other managers to achieve registration functionality.The device manager 336 may be responsible for managing the devicesdiscovered by the tracking manager 308. The device manager 336 mayfurther store and/or maintain the logic for algorithms related to devicediscovery and update.

FIG. 4 illustrates an example community mobile device for use in atracking system environment, according to one embodiment. As shown, thecommunity mobile device 104 may include, but is not limited to, a userinterface manager 402, a tracking device manager 404, a database manager406, and a tracking manager 408, each of which may be in communicationwith one another using any suitable communication technologies. The userinterface manager 402, database manager 406, and tracking manager 408illustrated in FIG. 4 may include similar features and functionality asthe user interface manager 302, database manager 306, and trackingmanager 308 described above in connection with FIG. 3 . It will berecognized that although managers 402-408 are shown to be separate inFIG. 4 , any of the managers 402-408 may be combined into fewermanagers, such as into a single manager, or divided into more managersas may serve a particular embodiment.

The community mobile device 104 may include a tracking device manager404. The tracking device manager 404 may facilitate scanning for nearbytracking devices 106. In some configurations, the tracking devicemanager 404 can continuously or periodically scan (e.g., once persecond) for nearby tracking devices 106. The tracking device manager 404may determine whether to provide an updated location of the nearbytracking device 106 to the tracking system 100. In some configurations,the tracking device manager 404 provides a location of a nearby trackingdevice 106 automatically. Alternatively, the tracking device manager 404may determine whether the location of the tracking device 106 has beenrecently updated, and may determine whether to provide an updatedlocation based on the last time a location of the tracking device 106has been updated (e.g., by the community mobile device 104). Forexample, where the community mobile device 104 has provided a recentupdate of the location of a tracking device 106, the tracking devicemanager 404 may decide to wait a predetermined period of time (e.g., 5minutes) before providing an updated location of the same trackingdevice 106.

In one configuration, the tracking device manager 404 may receive andprocess a location request or other information relayed to the communitymobile device 104 by the tracking system 100. For example, the trackingdevice manager 404 may receive an indication of a tracking device 106that has been indicated as lost, and provide a location of the trackingdevice 106 if it comes within proximity of the community mobile device104. In some configurations, the community mobile device 104 isconstantly scanning nearby areas to determine if there is a trackingdevice 106 within a proximity of the community mobile device 104.Therefore, where a tracking device 106 that matches information providedby the tracking system 100 (e.g., from the location request) comeswithin proximity of the community mobile device 104, the tracking devicemanager 404 may generate and transmit a response to the location requestto the tracking system 100, which may be provided to the user 103associated with the tracking device 106. Further, generating andtransmitting the response to the tracking request may be conditioned onthe status of the tracking device 106 being flagged as lost by themobile device 102 and/or the tracking system 100.

The tracking device manager 404 may additionally provide otherinformation to the tracking system 100 in response to receiving thetracking request. For example, in addition to providing a location ofthe community mobile device 104, the tracking device manager may providea signal strength associated with the location to indicate a level ofproximity to the location of the community mobile device 104 provided tothe user 103. For example, if a signal strength is high, the locationprovided to the user 103 is likely to be more accurate than a locationaccompanied by a low signal strength. This may provide additionalinformation that the user 103 may find useful in determining the preciselocation of tracking device 106.

As described above, the tracking device manager 404 may determinewhether to send a location within the proximity of the tracking device106 to the tracking system 100. The determination of whether to send alocation to the tracking system 100 may be based on a variety offactors. For example, a tracking device manager 404 may determine tosend a location of the tracking device 106 to a tracking system 100based on whether the detected tracking device 106 has been indicated aslost or if a tracking request has been provided to the community mobiledevice 104 for the particular tracking device 106. In someconfigurations, the community mobile device 104 may send an update of alocation of a tracking device 106 even if the tracking device 106 is notassociated with a current tracking request or if the tracking device 106is not indicated as lost. For example, where the location of a trackingdevice 106 has not been updated for a predetermined period of time, thecommunity mobile device 104 may provide an update of a tracking devicelocation to the tracking system 100, regardless of whether a trackingrequest has been received.

In some configurations, the community mobile device 104 may includeadditional features. For example, the community mobile device 104 mayallow a tracking system 100 to snap and download a photo using photofunctionality of the community mobile device 104. In someconfigurations, this may be an opt-in feature by which a community user105 permits a tracking system 100 to take a snap-shot and possiblyprovide a visual image of an area within a proximity of the trackingdevice 106.

FIG. 5 illustrates an example tracking device for use in a trackingsystem environment, according to one embodiment. The tracking device 106of FIG. 5 includes an interface 502, a transceiver 504, a controller506, and one or more sensors 508. The transceiver 504 is a hardwarecircuit capable of both transmitting and receiving signals. It should benoted that in other embodiments, the tracking device 106 includes fewer,additional, or different components than those illustrated in FIG. 5 .

The interface 502 provides a communicative interface between thetracking device 106 and one or more other devices, such as a mobiledevice 102. For instance, the interface 502 can instruct the transceiver504 to output beacon signals as described above (for example,periodically or in response to a triggering event, such as a detectedmovement of the tracking device 106). The interface 502 can, in responseto the receiving of signals by the transceiver 504 from, for instance,the mobile device 102, manage a pairing protocol to establish acommunicative connection between the tracking device 106 and the mobiledevice 102. As noted above, the pairing protocol can be a BLEconnection, though in other embodiments, the interface 502 can manageother suitable wireless connection protocols (such as WiFi, GlobalSystem for Mobile Communications or GSM, and the like).

The controller 506 is a hardware chip that configures the trackingdevice 106 to perform one or more functions or to operate in one oroperating modes or states. For instance, the controller 506 canconfigure the interval at which the transceiver broadcasts beaconsignals, can authorize or prevent particular devices from pairing withthe tracking device 106 based on information received from the devicesand permissions stored at the tracking device, can increase or decreasethe transmission strength of signals broadcasted by the transceiver, canconfigure the interface to emit a ringtone or flash an LED light, canenable or disable various tracking device sensors, can enable or disablecommunicative functionality of the tracking device 106 (such as a GSMtransmitter and receiving), can configure the tracking device into asleep mode or awake mode, can configure the tracking device into a powersaving mode, and the like. The controller 506 can configure the trackingdevice to perform functions or to operate in a particular operating modebased on information or signals received from a device paired with orattempting to pair with the tracking device 106, based on an operatingstate or connection state of the tracking device 106, based onuser-selected settings, based on information stored at the trackingdevice 106, based on a detected location of the tracking device 106,based on historical behavior of the tracking device 106 (such as aprevious length of time the tracking device was configured to operate ina particular mode), based on information received from the sensors 508,or based on any other suitable criteria.

The sensors 508 can include motion sensors (such as gyroscopes oraccelerators), altimeters, orientation sensors, proximity sensors, lightsensors, or any other suitable sensor configured to detect anenvironment of the tracking device 106, a state of the tracking device106, a movement or location of the tracking device 106, and the like.The sensors 508 are configured to provide information detected by thesensors to the controller 506.

Inferring Tracking Device Ownership

As noted above, a tracking device may be transferred between ownersduring the course of the tracking device's life span. Accordingly,enabling new owners to claim ownership of a tracking device within atracking system can beneficially improve the experience of new owners byunlocking the full functionality of the tracking device and trackingsystem for the new owners. FIG. 6 illustrates an example environment inwhich a user may claim ownership of a tracking device, according to oneembodiment. The user 103 may be in an environment with the mobile device102 and another tracking device 605. The tracking device 605 is distinctfrom the tracking device 106, and may not be initially associated withthe user 103 and the mobile device 102.

The mobile device 102 may detect the presence of the tracking device605, for instance when the tracking device 605 is within a thresholdproximity of the mobile device 102. The mobile device 102 may determinethat the tracking device 605 is not associated with or owned by the user103, and can detect that the tracking device 605 has been near the user103 for more than a threshold amount of time.

In one embodiment, after determining that the tracking device 605 hasbeen within a threshold distance or proximity of the mobile device 102for more than a threshold amount of time, the mobile device 102 candesignate tracking device 605 as a “candidate tracking device,” or“candidate device.” In other embodiments, the tracking device 605 can bedesignated a candidate device based on different or additional criteria,such as a geographic region within which the tracking device 605 islocated, a time of day or day of the week during which the trackingdevice 605 is within range of the mobile device 102, or based on anyother suitable criteria.

In response to the tracking device 605 being designed a candidatedevice, the mobile device 102 may prompt the user to claim ownership ofthe tracking device 605. For instance, a user interface associated withthe tracking system 100 and displayed by the mobile device 102 may bemodified by displaying one or more user interface elements, such as theprompt 630. In other embodiments, the mobile device 102 may display anotification that prompts the user to claim ownership of the trackingdevice 605. The user 103 may respond to the prompt 630 by a userinteraction with one or more user interface elements on mobile device102's screen, for instance an interaction claiming ownership of thetracking device 605 or denying ownership of the tracking device 605. Forexample, in the embodiment of FIG. 6 , when a user taps on the buttonlabeled “Yes” within prompt 630, the mobile device 102 providesconfirmation of the ownership claim by the user 103 of the trackingdevice 605 to the tracking system 100.

In some embodiments, when a user claims ownership of a tracking device,the user must authenticate himself or herself as a rightful owner of atracking device before a tracking system will associate the user as anowner of the tracking device. For instance, a first owner of a trackingdevice can register a password or other requisite credential with thetracking system, and can provide the password or credential to a userafter transferring the tracking device to the user. The user, inresponse to claiming ownership of the tracking device when prompted, canbe prompted a second time to provide the password or credential toverify that the ownership claim is legitimate (of course, the user canbe prompted to enter the password or the credential during the initialownership claim prompt as well). This beneficially provides a layer ofsecurity that prevents users from illegitimately claiming ownership ofdevices that they don't own.

In response to the mobile device 102 communicating the ownership claimby the user 103 of the tracking device 605 to the tracking system 100,the tracking system 100 updates an ownership record associated with thetracking device 605 to reflect the ownership of the tracking device 605by the user 103. In some embodiments, the tracking system 100 removes aninitial owner of the tracking device 605 (the owner of the trackingdevice prior to the user 103) when associating the user 103 as the ownerof the tracking device 605. In other embodiments, the tracking system100 updates the ownership record associated with the tracking device 605to include the user 103 without removing other owners identified by theownership record, for instance until the other owners are manuallyremoved or until other criteria are met (such as the passage of athreshold amount of time since an owner has interacted with or beenwithin range of the tracking device 605). It should also be noted thatthe user may manually claim ownership of tracking device 605 prior toreceiving notification 630, for instance via mobile device 102 oranother system connected to tracking system 100.

FIG. 7 is a flow chart of a method for claiming ownership of a trackingdevice, according to one embodiment. The mobile device 102 receives 710a beacon signal or other communication from a nearby tracking device605, for instance a tracking device within a threshold distance orproximity of the mobile device 102.

The mobile device 102 determines 720 that the nearby tracking device hasbeen within range of the mobile device 102 for more than a thresholdamount of time. In some embodiments, the threshold amount of time is anaggregate quantity of time (e.g., “more than 2 hours” or “more than 4days”). In other embodiments, the threshold amount of time is anaggregate quantity of time or a percentage of time over a particulartime interval (e.g., “more than 4 hours over the last two days” or “morethan 25% of the time over the last 10 hours”). In yet other embodiments,the threshold amount of time is a number of times that the mobile device102 has detected the tracking device 605 (e.g., “detected more than 4times” or “detected more than 10 times over the last week”). In yetanother embodiment, the threshold amount of time is a number of hours ordays over an interval of time in which the tracking device 605 has beendetected by the mobile phone 102 (e.g., “detected more than 12 of thelast 24 hours” or “detected each day this week”).

In some embodiments, a user can set the criteria associated with thethreshold amount of time used to identify a candidate owner, while inother embodiments, default criteria associated with the threshold amountof time can be used. For example, an owner can indicate that ownershipof a tracking device may have been transferred when the tracking devicehas been within 20 feet of a mobile device of another person for morethan 50% of the time in any given week. The criteria associated with athreshold amount of time used to identify a candidate owner can bestored by the tracking system 100.

A tracking device is identified 730 as a candidate tracking device inresponse to criteria associated with a change in ownership beingsatisfied (such as criteria associated with a threshold amount of timeused to identify a candidate owner), and a notification is generated 740for display via a mobile device prompting a user of the mobile device toclaim ownership of the candidate tracking device. Generally, the mobiledevice 102 checks for and/or receives communications from nearbytracking devices, and automatically uploads a location associated withthe mobile device and an identity of a tracking device from which acommunication was received to the tracking system 100. The trackingsystem 100 can then identify or flag the tracking device as a candidatetracking device, and can instruct the mobile device 102 to prompt a userof the mobile device to claim ownership to a detected tracking device ifthe criteria associated with a change in ownership are satisfied. Inother embodiments, the mobile device 102 can determine if the criteriaassociated with a change in ownership are satisfied and can prompt auser to claim ownership of the detected tracking device without explicitinstruction from the tracking server.

In response to a user claiming ownership of the tracking device (e.g.,via the generated notification or via an application associated with thetracking device), a response claiming ownership of the tracking deviceis provided 750 to the tracking system. The tracking system thenassociates 760 the tracking device with a user account associated withthe user, for instance enabling the user to take advantage offunctionality offered by the tracking device and/or tracking system(such as using the tracking system to locate the tracking device whenlost) that is not available to users that are not an owner of thetracking device. For example, a user can be prevented from seeing anidentity of a tracking device within a tracking device applicationrunning on a mobile device, even though the mobile device can receivecommunications from the tracking device and report the location of themobile device in conjunction with an identity of the tracking device toa tracking server. Thus, the user will be unable to determine, throughthe tracking device application, that the tracking device is within aproximity of the mobile device, that the mobile device has received acommunication from the tracking device, or the most recently observedlocation of the tracking device. However, upon designating the user asan owner of the tracking device, each of the features becomes availableto the user via the tracking device application.

The tracking system 100 may provide confirmation that the user has beenflagged as an owner of the tracking device, for instance via a visualdisplay notification within the user interface of mobile device 102. Inother embodiments, an interface associated with an applicationassociated with the tracking device can be modified to identify thetracking device and to indicate that the tracking device is owned by theuser.

In one embodiment, the tracking device 605 may be co-owned by more thanone user. For instance, the user 103 may explicitly inform the trackingsystem 100 that the tracking device 605 is a group tracking device orco-owned tracking device. Alternatively, a plurality of users' mobiledevices may all detect and identify the tracking device 605 as acandidate tracking device, and each user may claim ownership of thetracking device 605. In such instances, the tracking system 100 mayautomatically create a group of owners, each of whom is associated withthe tracking device 605 and able to utilize the functionality of thetracking device and the tracking system.

To illustrate a user claiming ownership of a tracking device, considerthe example of a user who buys a laptop to which a tracking device iscoupled. An application running on the mobile device of the user candetect the tracking device (e.g., by receiving communications from thetracking device and providing a location of the phone and an identity ofthe tracking device to the tracking system in response). The trackingserver can determine that the tracking device is within a thresholddistance of the mobile device for 75% of a 24-hour period, exceeding a50% ownership criteria threshold.

The tracking system, in response to determining that the 50% ownershipcriteria threshold has been exceeded within the previous 24-hour period,can instruct the tracking device application running on the mobiledevice of the user to prompt the user to claim ownership of the trackingdevice. The tracking device application, in response to receiving theinstruction from the tracking server, can prompt the user to claimownership of the candidate tracking device, for instance via a promptinterface element or notification (such as the prompt interface elementillustrated in FIG. 6 ). Once the user claims ownership of trackingdevice, the mobile device provides an indication of the ownership claim,an identity of the user, and an identity of the tracking device to thetracking server, which associates the user as an owner of the trackingdevice. The user can then view the tracking device within the trackingdevice application, for instance within a “my tracking devices”interface that identifies each tracking device associated with or ownedby the user and/or objects to which the tracking device are coupled(such as the laptop purchased by the user). Thus, a user is beneficiallyable to claim ownership of a tracking device via an automaticallygenerated ownership claim prompt without having to register a trackingdevice with the tracking system, thus saving the user time andincreasing the convenience of the user (and thus improving the user'sexperience with the tracking device).

Additional Considerations

The foregoing description of the embodiments of the invention has beenpresented for the purpose of illustration; it is not intended to beexhaustive or to limit the invention to the precise forms disclosed.Persons skilled in the relevant art can appreciate that manymodifications and variations are possible in light of the abovedisclosure.

Any of the devices or systems described herein can be implemented by oneor more computing devices. A computing device can include a processor, amemory, a storage device, an I/O interface, and a communicationinterface, which may be communicatively coupled by way of communicationinfrastructure. Additional or alternative components may be used inother embodiments. In particular embodiments, a processor includeshardware for executing computer program instructions by retrieving theinstructions from an internal register, an internal cache, or othermemory or storage device, and decoding and executing them. The memorycan be used for storing data or instructions for execution by theprocessor. The memory can be any suitable storage mechanism, such asRAM, ROM, flash memory, solid state memory, and the like. The storagedevice can store data or computer instructions, and can include a harddisk drive, flash memory, an optical disc, or any other suitable storagedevice. The I/O interface allows a user to interact with the computingdevice, and can include a mouse, keypad, keyboard, touch screeninterface, and the like. The communication interface can includehardware, software, or a combination of both, and can provide one ormore interfaces for communication with other devices or entities.

Some portions of this description describe the embodiments of theinvention in terms of algorithms and symbolic representations ofoperations on information. These algorithmic descriptions andrepresentations are commonly used by those skilled in the dataprocessing arts to convey the substance of their work effectively toothers skilled in the art. These operations, while describedfunctionally, computationally, or logically, are understood to beimplemented by computer programs or equivalent electrical circuits,microcode, or the like. Furthermore, it has also proven convenient attimes, to refer to these arrangements of operations as modules, withoutloss of generality. The described operations and their associatedmodules may be embodied in software, firmware, hardware, or anycombinations thereof.

Any of the steps, operations, or processes described herein may beperformed or implemented with one or more hardware or software modules,alone or in combination with other devices. In one embodiment, asoftware module is implemented with a computer program productcomprising a computer-readable medium containing computer program code,which can be executed by a computer processor for performing any or allof the steps, operations, or processes described.

Embodiments of the invention may also relate to an apparatus forperforming the operations herein. This apparatus may be speciallyconstructed for the required purposes, and/or it may comprise ageneral-purpose computing device selectively activated or reconfiguredby a computer program stored in the computer. Such a computer programmay be stored in a non-transitory, tangible computer readable storagemedium, or any type of media suitable for storing electronicinstructions, which may be coupled to a computer system bus.Furthermore, any computing systems referred to in the specification mayinclude a single processor or may be architectures employing multipleprocessor designs for increased computing capability.

Embodiments of the invention may also relate to a product that isproduced by a computing process described herein. Such a product maycomprise information resulting from a computing process, where theinformation is stored on a non-transitory, tangible computer readablestorage medium and may include any embodiment of a computer programproduct or other data combination described herein.

Finally, the language used in the specification has been principallyselected for readability and instructional purposes, and it may not havebeen selected to delineate or circumscribe the inventive subject matter.It is therefore intended that the scope of the invention be limited notby this detailed description, but rather by any claims that issue on anapplication based hereon. Accordingly, the disclosure of the embodimentsof the invention is intended to be illustrative, but not limiting, ofthe scope of the invention, which is set forth in the following claims.

What is claimed is:
 1. A method for identifying an ownership of atracking device, comprising: detecting, by a mobile device, a trackingdevice within a proximity of the mobile device in response to receivinga communication from the tracking device; in response to the trackingdevice being within the proximity of the mobile device for greater thana threshold percentage of time within a previous pre-determined intervalof time, prompting the user to claim ownership of the tracking deviceand requesting a password from the user set by a previous owner of thetracking device; and in response to receiving the password set by theprevious owner of the tracking device from the user of the mobiledevice, identifying, by the mobile device, the tracking device and theuser to a tracking server, the tracking server configured toauthenticate the user as a rightful owner of the tracking device andsubsequently associate the tracking device with a user account of theuser; wherein the mobile device is configured to receive an identity ofthe tracking device and provide the received identity of the trackingdevice to the tracking server without displaying the identity of thetracking device to the user via a mobile device application before theuser is authenticated as the rightful owner of the tracking device, andwherein the mobile device is configured to modify an interface of themobile device to display the received identity of the tracking device tothe user via the mobile device application after receiving confirmationfrom the tracking server that the user is authenticated as the rightfulowner of the tracking device.
 2. The method of claim 1, whereinprompting the user to claim ownership of the tracking device comprisesgenerating a notification including a user interface element within aninterface of the mobile device that, when selected, communicates theownership claim to the tracking server.
 3. The method of claim 1,wherein associating the tracking device with the user account of theuser comprises disassociating the tracking device with a user account ofa previous owner.
 4. The method of claim 1, wherein the tracking deviceis co-owned by a group of multiple owners, and wherein associating thetracking device with the user account of the user comprises adding theuser to the group of owners.
 5. The method of claim 1, furthercomprising enabling the user to access one or more functions of thetracking device or the tracking server in response to associating thetracking device with the user account of the user.
 6. The method ofclaim 1, wherein the communication comprises a beacon signalperiodically broadcasted by the tracking device.
 7. A non-transitorycomputer-readable storage medium storing executable instructions foridentifying an ownership of a tracking device, the instructionsconfigured to, when executed by the hardware processor, cause thehardware processor to perform steps comprising: detecting, by a mobiledevice, a tracking device within a proximity of the mobile device inresponse to receiving a communication from the tracking device; inresponse to the tracking device being within the proximity of the mobiledevice for greater than a threshold percentage of time within a previouspre-determined interval of time, prompting the user to claim ownershipof the tracking device and requesting a password from the user set by aprevious owner of the tracking device; and in response to receiving thepassword set by the previous owner of the tracking device from the userof the mobile device, identifying, by the mobile device, the trackingdevice and the user to a tracking server, the tracking server configuredto authenticate the user as a rightful owner of the tracking device andsubsequently associate the tracking device with a user account of theuser; wherein the mobile device is configured to receive an identity ofthe tracking device and provide the received identity of the trackingdevice to the tracking server without displaying the identity of thetracking device to the user via a mobile device application before theuser is authenticated as the rightful owner of the tracking device, andwherein the mobile device is configured to modify an interface of themobile device to display the received identity of the tracking device tothe user via the mobile device application after receiving confirmationfrom the tracking server that the user is authenticated as the rightfulowner of the tracking device.
 8. The non-transitory computer-readablestorage medium of claim 7, wherein prompting the user to claim ownershipof the tracking device comprises generating a notification including auser interface element within an interface of the mobile device that,when selected, communicates the ownership claim to the tracking server.9. The non-transitory computer-readable storage medium of claim 7,wherein associating the tracking device with the user account of theuser comprises disassociating the tracking device with a user account ofa previous owner.
 10. The non-transitory computer-readable storagemedium of claim 7, wherein the tracking device is co-owned by a group ofmultiple owners, and wherein associating the tracking device with theuser account of the user comprises adding the user to the group ofowners.
 11. The non-transitory computer-readable storage medium of claim7, wherein the instructions, when executed, cause the hardware processorto perform further steps comprising enabling the user to access one ormore functions of the tracking device or the tracking server in responseto associating the tracking device with the user account of the user.12. The non-transitory computer-readable storage medium of claim 7,wherein the communication comprises a beacon signal periodicallybroadcasted by the tracking device.
 13. A system for identifying anownership of a tracking device, comprising: a hardware processor; anon-transitory computer-readable storage medium storing executableinstructions that, when executed by the hardware processor, cause thesystem to perform steps comprising: detecting, by the system, a trackingdevice within a proximity of the system in response to receiving acommunication from the tracking device; in response to the trackingdevice being within the proximity of the system for greater than athreshold percentage of time within a previous pre-determined intervalof time, prompting the user to claim ownership of the tracking deviceand requesting a password from the user set by a previous owner of thetracking device; and in response to receiving the password set by theprevious owner of the tracking device from the user of the system,identifying, by the system, the tracking device and the user to atracking server, the tracking server configured to authenticate the useras a rightful owner of the tracking device and subsequently associatethe tracking device with a user account of the user; wherein the systemis configured to receive an identity of the tracking device and providethe received identity of the tracking device to the tracking serverwithout displaying the identity of the tracking device to the user via asystem application before the user is authenticated as the rightfulowner of the tracking device, and wherein the system is configured tomodify an interface of the mobile device to display the receivedidentity of the tracking device to the user via the system applicationafter receiving confirmation from the tracking server that the user isauthenticated as the rightful owner of the tracking device.
 14. Thesystem of claim 13, wherein prompting the user to claim ownership of thetracking device comprises generating a notification including a userinterface element within an interface of the system that, when selected,communicates the ownership claim to the tracking server.
 15. The systemof claim 13, wherein associating the tracking device with the useraccount of the user comprises disassociating the tracking device with auser account of a previous owner.
 16. The system of claim 13, whereinthe tracking device is co-owned by a group of multiple owners, andwherein associating the tracking device with the user account of theuser comprises adding the user to the group of owners.
 17. The system ofclaim 13, wherein the communication comprises a beacon signalperiodically broadcasted by the tracking device.